Add Cardputer ADV Keyboard support #204
Conversation
uh @echo-lalia i know i'm doing it wrong but how badly |
|
Not too bad as far as i can tell at a glance! There's a couple of scripts you have to run before that script works correctly, which will build the Micropython board folder for each device. You should be able to run |
|
Bootloop (m5launcher+compiled bin, not reaching launcher screen tho) |
it's bootlooping enough that the notification daemon is glitching |
I'm not certain. MicroHydra does work with M5launcher, but installing Micropython using M5launcher (as well as some other tools, such as M5burner) can be temperamental thanks to issues mounting/creating the filesystem. Have you tried installing through Thonny, with the "erase-flash" box checked? (Installing it that way has always worked for me with this board). And if that doesn't boot into MicroHydra, are you at least able to get a MicroPython repl when connecting from Thonny? |
|
This is the compiled bin, lemme try doing a proper flash I tried and I got to a REPL but nothing happened |
|
i know dashes have a little bit of a problem so i'll retry now maybe it's because there's a dedicated version of micropython for the cardputer but not for adv? or maybe it was circutpython i don't remember |
|
Looks like you flashed the generic esp32s3 Micropython variant. If you click the little hamburger menu, you can select a Micropython bin from your own computer, and flash MicroHydra that way. (You can use esp-tool as well, but you do have to erase the flash first) If you can get a Micropython repl after flashing the MicroHydra bin, you should be about to check the log.txt file and hopefully find some informative error description. |
|
I tried pressing the hambuger and selected the CARDPUTER_ADV.bin and it did not accept it and.... i got a bootloop D: |
|
Just tried pulling your changes and uploading the cardputer_adv.bin firmware to my regular Cardputer, and it (kinda) worked! I got a MicroPython repl through Thonny (though it took a few tries to catch it as it was bootlooping), and I was able to see the log.txt for what was going wrong: I never ended up documenting the If you would like to keep working on this and get it working, I'd suggest installing a plain MicroPython firmware onto the device, uploading the compiled MicroHydra .mpy files to it, and then uploading the _keys.py file and edit/test it that way, rather than building/uploading a firmware to test your additions :) |
echo-lalia
added
enhancement
|
I have attempted to redo the keymap, from scratch. |
|
I have attempted to fix the i2c issue so i'm trying to rebuild (sidenote: i hate make, but if you aren't gonna provide a makefile at least make the script names more understandable) EDIT: viper is REALLY not liking this, for now i'm disabling it for the function. Later i might fix it and re add it |
|
MicroHydra does a soft reset in-between apps, which Thonny absolutely hates unfortunately. When the running app errors, main.py catches and logs the error in log.txt, then starts the launcher (causing another soft reset). Which makes it a bit annoying to monitor using Thonny. To get around that, I usually just directly run the launcher.py (or whatever app I want to test) from Thonny by hitting F5 with the .py file open. Or, by importing the app using something like |
ok so now i got a log, yippe, but uhhhhhhhhhh still an error that i dont understand |
|
I created this driver file as well as modified the _keys file. Seems like a working example. I replaced the _keys file and added the tca8418 file in my lib.userinput folder. I am new to this and don't know how to contribute properly. |
|
@carnitashredder Here's how to GitHub:
|
|
@TheOddCell Awesome. Thanks for the tip! |
3 participants
This does not add anything else
I am unsure how to build this tbh so for now this is a draft
Resolves #203